While the fill-test-ci-values target's dependency on install-registry
was correctly manipulated by the SKIP_INSTALL_REGISTRY variable, the
install-lagoon-build-deploy target had a hard-coded dependency on
install-registry. The result was that the registry would get installed
multiple times anyway via the fill-test-ci-values target via an indirect
dependency.

Fix that by removing the dependency that install-lagoon-build-deploy has
on install-registry when SKIP_INSTALL_REGISTRY=true.

fix: avoid installing the registry multiple times

chore: modify keycloak healthcheck endpoint for newer keycloak

Set 1.28 as default for tests, also test 1.29

…ote-bug-fix

chore: remove dioscuri subchart from lagoon-remote

Support Keycloak migrations via the API init-container

feat: add log streaming option to ssh-portal

Using `localhost` and port `3306` forces mysqladmin to connect to `127.0.0.1`
via TCP, instead of via socket. The uselagoon/mariadb images only set a root
password for `localhost`, so the attempt to authenticate via `127.0.0.1` fails.

The current TCP based readiness probe causes an `Aborted connection` log for
each check. Changing it to the `readiness-probe.sh` script removes the log and
also ensures that mysqld is able to serve SQL requests, not just that it can
open a socket.

The mariadb init script starts mysqld multiple times, so a TCP check will
signal startup is complete before the init is actually finished.

- livenessProbe access denied warnings
- readinessProbe aborted connection warnings
- startupProbe waits for mariadb init to complete
- add configurable terminationGracePeriod

feat: apiDB/keycloakDB startup/readiness/liveness probes and startup/shutdown time